Hi @duncanfinney . Thanks for this. Are there any downsides you can see, or things we might need to mention in the documentation? For example would we need to advise anyone who hast the @types/turf workaround installed to remove it?

Took a closer look at the error message and think we might need to look into this in more detail.

The message says:

There are types at ‘/home/…/@turf/intersect/dist/js/index.d.ts, but this result could not be resolved when respecting package.json “exports”.

To summarise, the types are in the package, referenced from the "types" field in package.json which is as it should be. Volar finds them, but some other configuration prevents it resolving them confidently. Does that sound accurate to you?

Rather than duplicate the d.ts in the package, I'd lean more towards correcting the exports field (if that's the issue) so that Volar can be confident to use the types it does find. Are you open to doing a little hacking about in your local node_modules directory to try a few options?

@duncanfinney going to retire this PR in favour of #2555 which should have Turf export declaration files more predictably and consistently. Once the next alpha drops (alpha.3 by my count) please give it a try and raise an issue if you run into problems.